Cloudron Forum

Running an alternate mail server on Cloudron is unlikely. Automated provisioning of email setup of apps is part of the product (from v1 of Cloudron) and this would break if we supported other mail servers.

yes, direct url is working again. That was it! Applied the one line change on all three servers here and the 60 query test goes from 20/60 to 60/60 on each of them. For reference, temperror was running at 48%, 34% and 18% of inbound mail over the last 24 hours on those three. I will report back once enough new mail has come in to see where it lands. Thanks for digging into this so quickly.

Hello @diego @diego said: However, from a system design perspective, I was wondering if it would be better to: keep the system disk small (OS + Cloudron core) attach a separate disk dedicated to mail storage Yes you can do that. I also do that with my private Hetzner server so I can scale up the CPU/RAM and have the storage seperate. @diego said: Will the Cloudron backup system still include it normally? Yes. If you move e.g.: /home/yellowtent/boxdata/mail to /mnt/sdd1 and create a symlink so /home/yellowtent/boxdata/mail => /mnt/sdd1 this still works. What you can always to is creating a small Cloudron server to test and tinker as much as you like. This way you get a better feeling for everything without risking any damage to production.

@czeimke can you update to 8.2.3 ? Is this still a problem?

@CRBear said in Mail server: IP address verification?: Am I correct in understanding that the email server checks from which IP address a connection is established to send an email and by default, it verifies against the Spamhaus blacklist? The mail server does not make any check for outbound email. The various checks you see in the Email Status tab are purely diagnostic. The idea is if one or more checks are failing there, most likely the email won't be delivered. The Spamhaus is checked for inbound emails though. The DNSBL zone against which it checks is configurable at https://docs.cloudron.io/email/#dnsbl